feature: support client_secret_post #92
Conversation
client_secret_post means client_id and client_secret in body of request not in authorization header
|
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/186000366 The labels on this github issue will be updated when the story is started. |
|
| GitGuardian id | Secret | Commit | Filename | |
|---|---|---|---|---|
| 8047040 | Base64 Basic Authentication | 6b86b95 | spec/token_issuer_spec.rb | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
|
created this after review of #90 |
|
Can somone please review this |
client_secret_post means client_id and client_secret in body of request not in authorization header